Issue 6925 inventory builder tests failing #6926
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
tox
's Python requirement from 3.3 (deprecated) to 3.xWhich issue(s) this PR fixes:
Fixes #6925
Special notes for your reviewer:
The PEP8 parts are minor, and the Python version change is probably the biggest change here.
For the initial PR I've gone with whatever
python3
means on a user's system as this caters for a wide range of developer platforms (Ubuntu 20.04 ships with Python 3.8, CentOS 8 ships with Python 3.6 and so on) and should mean less maintenance in future as Python keeps moving.However this opens us up to CI failures and potential inconsistencies if in future there are breaking changes between Python versions.
Personally I get the impression that the inventory-builder is a small enough and infrequently-enough changed piece of code that it's probably preferable to take the more simple path, and to be notified by CI pain if something breaks in future. However I'm happy to change this and pin to a more specific version if anyone feels strongly.
Does this PR introduce a user-facing change?: